InfoMagic Internet Tools 1995 April/Internet Tools.iso/dos_win/winsock/maillist/94-03.Z/94-03/text0137.txt

Text File | 1994-03-30 | 26.1 KB | 693 lines

Hello there,

    I have installed the windows sockets TCP/IP support and I am
experiencing the following problems:

1. When I am running telw.exe which is the telnet for winsock and set the
terminal to vt100 from a UNIX shell using the command, "set term=vt100" and
then run the vi editor then I get a general protection fault error from
windows.....It seems that I cannot set  up the terminal corredctly so that I
can run the vi editor........None of the cursor keys seem to work and none of
the h,j, k, and l keys work so that I can move up down left and right inside
the vi editor.....Can anybody tell me whether there is a new versio that fixes
that problem? Is there any way around it?

2. Also, I would like to get some documentation about this winsock
program...How do you use the programs view.exe, winarchie.exe, winchat.exe
etc....I can run them but I do not seem to be able to do anything with
them......

3. The readme file for the winsock trumpet talks about some debug flags...I am
running on ethernet...The command that I would need to specify in the program
manager item is

        tcpman.exe -debug=ethernet   ?????



    I would very much appreciate any relevant response.

    Please e-mail...If anyone is interested in the responses  then please
let me know..I can mail all the  responses I get...

Thanks, in advance

Chris

E-mail Address: [e-mail]
From [e-mail] Fri Mar 11 04:11:09 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA07064; Fri, 11 Mar 1994 00:28:26 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA14050; Fri, 11 Mar 1994 00:04:50 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 11 Mar 1994 04:11:09 GMT
From: [e-mail] (aburger)
Message-Id: <2lor0t$[e-mail]>
Organization: HookUp Communication Corporation, Waterloo, Ontario, CANADA
Sender: ses
References: <2lb6bb$[e-mail]>, <[e-mail]>
Subject: Re: Winsock SLIP script

In article <[e-mail]>, [e-mail] (Chenglung Eric Yen) says:
>
>In article <2lb6bb$[e-mail]> [e-mail] ([e-mail]) writes:
>>From: [e-mail] ([e-mail])
>>Subject: Winsock SLIP script
>>Date: 5 Mar 1994 23:58:35 GMT
>
>>Is there any documentation on how to write Winsock dialing scripts for SLIP users?
>
>Yes, of course there is a document on writing the script for the SLIP dialup.
>Read the document named install.doc. It should be in your winsock subdirectory.

The copy of Winsock I had didn't have the docs..  Strange.  I ended up getting
the new version (v1.0 shareware).

Thanks.

Alex
From [e-mail] Thu Mar 10 20:59:56 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA07072; Fri, 11 Mar 1994 00:28:27 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA09445; Fri, 11 Mar 1994 00:05:49 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 10 Mar 1994 20:59:56 GMT
From: [e-mail]
Message-Id: <2lo1oc$[e-mail]>
Organization: Rensselaer Polytechnic Institute, Troy, NY
Sender: ses
Subject: Re: nfs client for winsock?

In article <2lnmqr$[e-mail]> [e-mail] (Ryan Simmons) writes:
>In article <[e-mail]>, [e-mail] (mark smith) says:
>>
>>I am not sure whether it is possible or not, but I would like to see if there
>>are any winsock compliant nfs client packages out there.  All of the resources
>>I have found so far require the nfs client to run at dos time.
>
>(I feel like I'm beginning to sound like an advertisement for NetManage!  Geesh!)
>
>ChameleonNFS provides both an NFS client *and* server.  As I type this I'm nfs-mounted
>to a couple IBM RS6000 machines that are running a pcnfs daemon.  If I want, I can also
>let people mount to my machine the same way.  Those RS6000s are on my desktop (using
>Norton Desktop for Windows) just like any other drive, and I can copy, move, delete,
>rename, etc., as if all the files were local.  It's great!
>
>Of course, Chameleon is commercial, and if you're looking for public domain or
>shareware, then sorry, I can't help you.
>
>    ___                |[e-mail]
>   /   )               |[e-mail]
>  /__ /     __         |
> /   ) / / / / / )     |CIS 71212,530
>/   (_(_/_(_(_/ (_     |*I got rid of my laptop because my cat was jealous!*
>       /


Does ChameleonNFS require TSRs before loading Windows? (other than basic network
board drivers -- e.g. NDIS, PKT, ODI, etc.)

Where in PC-NFS 5.0 the following commands must be run at the DOS prompt before
loading windows:

   NET START RDR PC.IP.name *
   NET SUBNET 255.255.255.0
   NET ROUTE gateway.name
   NET PCNFSD auth.server.name
   NET LOGIN *

In ChameleonNFS nothing like this is required?

;-----------------------------------------------------------------------------;
;       Standard Disclaimer...                                                ;
;                                                                             ;
;       Rensselaer Polytechnic Institute -- 110 8th Street -- Troy, NY 12180  ;
;-----------------------------------------------------------------------------;

***
From [e-mail] Fri Mar 11 02:58:25 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA22256; Fri, 11 Mar 1994 02:58:25 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA21594; Fri, 11 Mar 1994 02:31:25 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Thu, 10 Mar 1994 20:50:28
From: [e-mail] (David B. Andersen)
Message-Id: <andersen.14.0@mink>
Organization: Intel Architecture Labs
Sender: ses
References: <[e-mail]>
Subject: Re: Transport Layer Interface (TLI)

In article <[e-mail]> jim@edscom (Jim Thomas) writes:
>From: jim@edscom (Jim Thomas)
>Subject: Transport Layer Interface (TLI)
>Date: 9 Mar 1994 16:09:36 -0000

>Having planned to implement a Winsock based server that was
>to communicate with a Unix box using the BSD socket interface
>I now find that the Unix box is to use a Transport Layer
>Interface (TLI) instead.

>Does anybody know if there is a MS-Windows based library or
>support routines (or anything) that can enable the Windows
>applications that I have already written to use TLI.

>If not, is there any other way that I could proceed, like
>some kind of protocol conversion in software or hardware.

>Thanks in anticipation

>Jim Thomas

>--
>Jim Thomas, EDS-Scicon Ltd,Wavendon,Wavendon Tower,Milton Keynes,MK17 8LX,UK
>[e-mail]   Tel:  [phone]
>Opinions expressed are my own, and are not necessarily those of my employer.

You don't really have a problem at all.  Remember that both Winsock and TLI
are *interfaces* and  not *protocols*.  As long as the protocols remain the
same (TCP/IP in this case) it doesn't matter what interface each side is
using.
=============++=============++=============++=============++====
David B. Andersen             Intel Architecture Labs
[e-mail]   or  [e-mail]
From [e-mail] Fri Mar 11 05:09:39 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA22263; Fri, 11 Mar 1994 02:58:27 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA19405; Fri, 11 Mar 1994 02:50:41 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 11 Mar 1994 05:09:39 GMT
From: [e-mail] (David B. Sussman)
Message-Id: <[e-mail]>
Organization: Brown University
Sender: ses
Subject: Having a bit of trouble Packet Driver

Just got some zip files from  cicia.indiana.edu
think i got
winsock.zip
winapps.zip
ws_ftp.zip
Ws_ping.zip
and the trumpet news reader  forgot what it was called..

I think I need a slip packet driver to load before my WINPKT driver.. ?
WHere is it and how do I get it?  DO i have the essential programs for
running slip at this moment?  Please,  any info will help..
mail to
         [e-mail]
From [e-mail] Fri Mar 11 04:45:02 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA24750; Fri, 11 Mar 1994 03:27:20 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA19217; Fri, 11 Mar 1994 03:27:12 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Fri, 11 Mar 1994 04:45:02 GMT
From: [e-mail] (Mark_Bramwell)
Message-Id: <[e-mail]>
Organization: Western Business School
Sender: ses
Subject: winsock telnet with xmodem transfer?

I have an outdial modem hooked to a terminal server.

I can  telnet into it and command the modem.  That is, if I type  AT [return]
I get 'OK'.  I can also dial out and connect to bbs machines.  I can't
download any files because I don't have a telnet type of program with file
transfer (x/y/zmodem).

Does such a thing exist?


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Mark Bramwell, VE3PZR                Located in sunny London, Ontario

Internet: [e-mail]  IP Address: 129.100.22.33
  Packet:  VE3PZR @ VE3GYQ               UWO Phone: [phone]
From [e-mail] Fri Mar 11 06:51:37 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA26737; Fri, 11 Mar 1994 03:58:26 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA27926; Fri, 11 Mar 1994 03:28:56 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: 11 Mar 1994 06:51:37 GMT
From: [e-mail] (Anton J Vuorilehto)
Message-Id: <2lp4dp$[e-mail]>
Organization: Helsinki University of Technology
Sender: ses
References: <[e-mail]>, <[e-mail]>, <[e-mail]>
Reply-To: [e-mail] (Anton J Vuorilehto)
Subject: Re: Chameleon memory management

In article <[e-mail]> [e-mail] (Charles Edwards) writes:
>In article <[e-mail]>, [e-mail] says:
>>
>>Mime-Version: 1.0
>>Date: Wed, 09 Mar 94 14:25:05 PDT
>>Lines: 18
>>
>>
>>..
>>> for lower memory. Chameleon allocates large blocks of memory in the
>>> first 1MB. When that area is exhausted, Telnet gives the divide by 0
>>> error. You should try to have as much conventional memory as possible
>>> available before starting Windows....etc
>>Charles:
>>Since this is the case, would it make sense to have an include
>>statement in EMM386 for B000-BFFF since I have a VGA monitor? According
>>to my books this area is reserved for MDA, CGA, EGA and VGA text.
>>I, like so many others, keep getting GPF's from MAIL.EXE. Do you see
>>a connection with GPF's and the way Chameleon handles lower memory?
>>------------------------------------------------------------
>
>It certainly won't hurt to free up as much conventional memory as possible.
>Unfortunatly, my S3 video uses this area even in VGA mode, so I can't
>allocate it to EMM386. If you can, by all means do so.
>
>I haven't been seeing GPFs myself. Just the divide by 0 in Telnet. And we
>don't use Chameleon mail at my office so I can't address that issue.
>
>There is a very good book called "Windows Internals" that has a chapter
>about Windows' handling of memory. It's actually kind of scary. For
>example, a DLL which has any FIXED segments, either code or data, will
>get that memory allocated as low as possible in the linear memory space.
>Windows will also PageLock these segments, which means they can't be
>swapped out to disk. Very few DLLs actually need to have pagelocked code
>or data and they certainly don't need it in the critical first megabyte.
>But many people don't know about this, and define their data segments
>FIXED in the DEF file. Maybe that's what happened with Chameleon.
>
>Of course, since Chameleon needs to communication with the real-mode NDIS
>driver (I'm assuming you have a direct network connection via an Ethernet
>or Token Ring card) maybe this data DOES have to be in the first megabyte.
>I just wish I could be sure that NetManage is being careful to only
>allocate low memory when absolutely required.
>
>I've spent most of the past 2 weeks investigating Windows memory management,
>primarily because of the issues with Chameleon, and the more I find out,
>the more depressed I become. We're trying to build a store-and-forward
>mail system on top of Chameleon, and exhausting the first megabyte has
>been a major stumbling block.
>
>********************************************
>* More than half the human beings who have *
>* ever lived are alive today.              *
>* So the experimental probibility of dying *
>* is less than 50%.                        *
>********************************************

Here is a copy of the article containing the win_wrap lower memory
management utility, it even got the sources for it...(for Netmanage
to study?)...
_____________________________________
WIN_WRAP


A Windows 3.1 program launcher that prevents the client app from
taking valuable 'low memory'. Kind of like a LOADHI for Windows.

Released to the public domain.

This posting includes source and uuencoded executable.

Short README:
------------
Have you ever run into the situation where you are trying to
launch a Windows app, and nothing happens? Perhaps you're out
of memory?

You know you have gobs of virtual memory left, and the Program
Manager AboutBox says that you've got 60% resources left. What gives?

It's possible that you have run into a little known Windows3.1
roadblock. Perhaps you're out of 'low memory'. This is the precious
memory below the 1 meg line. For an excellent discussion of this
problem, see the article by Matt Pietrek in the Oct/93 issue of
Microsoft Systems Journal.

If this is your problem, then a previous application has been loaded
which locked down some low memory. All apps require at least 512 bytes,
but some will take much more if they can. If the app (or apps) have
taken all the low memory, the Windows will refuse to launch anymore
apps (since it needs the 512 bytes), and will NOT give the user
any indication of what happened (or rather, what didn't happen).

If you can identify the offending app (or apps), then you can use
the WIN_WRAP program to launch it. WIN_WRAP will try to force
your app to load itself high in memory.

What WIN_WRAP does is: take ALL of the low memory; give back 1k;
launch your app; release back all of the rest of the memory to the system.

If your app requires locked memory, it will get it, but ABOVE the
1 meg line. When WIN_WRAP terminates (immediately after the client
app is launched), the low memory is freed up, so that lots of other
apps can run.

Since WIN_WRAP removes itself almost immediately, you can use it
many times in the same session.

I would like to suggest to everyone who is designing system-
status monitors that you include the 'space available below
the 1 meg line' as a valuable system parameter, in the same
league as:
    user/gdi free space
    global memory free space
    disk free space

------
Instead of running
    RECORDER.EXE textfile.txt
you can run
    WIN_WRAP RECORDER.EXE textfile.txt

In the former case, the RECORDER.EXE program will take 3 segments from the
low memory area:
    the TDB (task database)
    a code segment (about 11k)
    a data segment (about 2.5k)
In the latter case, the RECORDER.EXE program executes properly, but only
takes 1 segment from the low memory area: the TDB. The other two segments
are located in high memory, where there's lots of space.

You can put any valid command line after the WIN_WRAP command. These
compound commands may be put in your Program Manager icons on the
'Command Line' entry. (Hit Alt-Enter to view the icon-properties).

If you want WIN_WRAP to operate on programs in your Startup group, just
modify the CommandLine entries in the Startup group. I haven't figured
out how to use WIN_WRAP with the 'load=' and 'run=' options in the WIN.INI.

Long README:
-----------

Many applications use Windows functions that require 'callbacks'.
A 'callback' is the way that an application can register
itself for notification of system activity. The kind of
'callback's that I am referring to here are interrupt service code
segments, such as netbios client code, IPX client code, TCP/IP
client code.

This code MUST be in memory at all times. The proper way to ensure
that it is in memory is to lock it in place. There are two ways
to do that.

Method 1: Microsoft suggests that this kind of code be written in
a .DLL, and that the code+data segment be marked as FIXED. At .DLL load
time, Windows will load this code+data 'as low as possible' in the
Windows memory map (the Windows VM, actually). In a healthy machine,
this will be below the 1meg line. The segments are locked in place and
PageLocked.

Method 2: If the code+data to be executed resides in an .EXE file, then
the segments will be loaded high in the Windows memory map, and left
MOVEABLE. The programmer can, however, call GlobalPageLock() to lock
the memory in place. It appears, however, that just before Windows
locks down the memory, it moves it down into low Windows memory, and,
as above, in a healthy machine, this will be below the 1meg line.

The memory below the 1meg line is used for many things:
    -DOS for this VM
    -TSR's and device drivers for this VM
    -all GlobalDosAllocs()
    -DPMI buffers for this VM
    -a TDB (Task Data Base) segment, per app
The TDB must be located there, because it has to be accessed by
the Windows app (using a selector) and by DOS (using the equivalent
segment register). Windows will refuse to launch an app if it cannot
get the TDB into low memory.

Many apps require locked and PageLocked segments so that they can present
Windows with callback services.

You can see that both Method 1 and 2 will push the PageLocked memory as low
as possible, usually into this 'below 1meg' memory.

Most often, these segments (code+data) do not need to be in the first
meg of ram; i.e. they do not need to be accessed from real mode.

The application will allocate these segments using GlobalAlloc()+GlobalPageLock().
These segments are the ones that WIN_WRAP will push up high.

Sometimes an app WILL require low memory. It will request it from the system
by calling GlobalDosAlloc(). If you try to launch one of these apps with
WIN_WRAP, the GlobalDosAlloc() will fail, and the program will not launch.
These apps are not appropriate for WIN_WRAP.

The type of applications that I have used WIN_WRAP with are netbios
aware apps, TCP/IP client apps and .DLL's and IPX apps. Netbios
buffers may be located above the 1meg line, and IPX buffers can
be as well (if IPX is more recent than 09/92).

To help you visualize the activity of WIN_WRAP, I recommend
the BELOW1M application written by Matt Pietrek. You can also use
HEAPWALK, and sort by address. Look for addresses which start with 000
to indicate blocks below the 1 meg line.

The operation of WIN_WRAP is not guaranteed. Use it at your own risk.

WIN_WRAP is released to the public domain. As usual, I ask the courtesy
of feedback if you enhance this tool.

Pat Beirne
76475,3640
[e-mail]


///////////// source follows ////////////////////////////
///////////// win_wrap.cpp ////////////////////////////
/*SDOC*************************************************************

    $Header$

    Module: WIN_WRAP

    Author:    Pat Beirne

    Description: This is a wrapper application that takes one
        parameter on the command line. It then alloc's memory in
        such a way as to force the app to load (mostly) above the
        1 meg line.

        It does this by allocating all except 1k of low ram. Then
        it launches the balance of the command line.
        It then frees the allocated memory.

        If the slave app needs GlobalPageLock memory, it will take it from
        ABOVE the 1 meg line.

*************************************************************EDOC*/

/*SDOC*************************************************************

  Revision Record

    Rev    Date        Auth    Changes
    ===    ====        ====    =======

    0.0    10/11/93    pb      start

*************************************************************EDOC*/



/*
**
**     Includes
**
*/
#define STRICT 1
#include <windows.h>

/*::defn
**
**     Defines
**
*/

/*::end*/


/*::decl
**
**     Global Variables
**
*/

/*::end*/


/*::fnproto
**
**     Function Prototypes
**
*/

/*::end*/


/*
**
**     Local Variables
**
*/

int WINAPI WinMain(HINSTANCE hInst, HINSTANCE hPrevInst, LPSTR lpCmd, int nCmdShow)
{
    HGLOBAL h1;
    DWORD dw;
    WORD segBasic;
    VOID far * pFirst;            // root of the linked list
    VOID far * far *p;

  // allocate a 2k block to give back to the system
  segBasic = LOWORD(GlobalDosAlloc(2048));

    // allocate all of the rest of dos memory, 32k at a time
    p = &pFirst;

    while(1)
    {
        // allocate all of low dos memory, 32k at a time
        dw = GlobalDosAlloc(0x8000U);

        // fill the data into the first WORD of the previous seg, even
        // if dw==0 (end of list)
        *p = MAKELP(LOWORD(dw),0);
        if (*p==NULL) break;

        // form a pointer to the first WORD of the new seg
        p = (VOID far * far *)*p;
    }

    // repeat, alloc 2k at a time
    while (1)
    {
         dw = GlobalDosAlloc(2048);
         *p = MAKELP(LOWORD(dw),0);
         if (*p==NULL) break;
         p = (VOID far * far *)*p;
    }

    // now we have exhausted low ram; give back one small segment
    if (segBasic) GlobalDosFree(segBasic);

    // launch the client app
    int nRet =
        WinExec(lpCmd,nCmdShow);

    // give the client app time to settle-in
    MSG m;
    PeekMessage(&m,NULL,NULL,NULL,PM_NOREMOVE);

  //////////////////////////////////////////////////////////////////////
  // we can now release the list back to the system
  // free the dos memory

  // point to the start of the list
  p = (VOID far * far *) pFirst;
  while (p)
  {
      // keep the pointer to next (walking pointer)
      pFirst = *p;
      // free the block
    GlobalDosFree(HIWORD(p));
    // point to next
    p = (VOID far * far *) pFirst;
   }


  return nRet;
}

///////////// win_wrap.def ////////////////////////////
NAME WIN_WRAP
DESCRIPTION "Wrapper Application to Force High Load"
EXETYPE Windows
STUB "winstub.exe"
HEAPSIZE 1024

[ Section: 1/1  File: WW.ZIP  Encoder: Wincode v1.5 ]
Original Input File Size: 2436

begin 644 WW.ZIP
M4$L#!!0`!``(`+A;:QN_8QC1"@D``"`1```,````5TE.7U=205`N15A%[5=]
M;!/G&7_N;)\=AQB+!8.ZXAPL-=\9Q,7=1/@(*(9`2)QDV'R$9"$QX-+$J7V7
ML&J"4%>4VQL@0E7:6=LT2L58E**L19H=-`A)@$++B+-)34,[=>&C3@]8%BH2
M4NK;<^>$!$31]L?^J#9;=\][S^?O>=[GO?>]=9O>`A4`L'A)DA:`<B_'(<@W
M2AX\[:=^FO#_LN]"!:*%\),='C];Y?-N]Y56L#[WR[S'Y_:SZSQE/J_?NXUC
M79[*<F^-/RU)G\K^F[]-AI23"9>GAZB<R]._"U7XW\68FZ5)KQA9Z;2*!E##
MK&>49QKD_QQ\$SCP7P0_A4IEO<LW6I<#YY'J5;F0E[`\*2^A'V)4YH08I7-E
MYY:X"C(=**5`!\"LS2K(S<I1KR_,*@"+RU=:5>7VL9E552]YRDHYC[>2Y;RL
MW>LK<[.K/=MWL#G>TO+_XG1(4K/D"'Y&L0G6V^N#D@20V,K=JF/LL/<L4+Y>
MP6`$P38)A*7)()A-4,=,!<'T#"BJ^SJ.KH:3"](&&2,FQVD5IDA?GGXT!U"V
M!D8DO*89WLX#:ZM#T9!LR7%[#+4WV`]3(?A7^@T(.M6_A*B+D6RO@61[%:]:
M"';`;R#0P3B"5ZCW(#09^F:IH:Z[/FL]N64^V"U[DA"=9)N*EPDO1`:Z4Q"X
M39,;*5O6?3BF&X)%8T"+L:0R4,&<CBD]#X:4$#S7<E,]IJ'%M[VL84HAAK?A
MVNR#6!(+L<V#(^\`,1T#ZU7)_%OPJ_I>H8X<1TXCG%*!S(HK&N;!M:4'SUHE
M2^T2X)X/)\'I5+A[C$L,2WNLK0,G^.GB#<:L32	S;`']1-\S)]25V?'Y:I
M1M_6*-XQI9QN@C--$.V%D<$GHX/.)Z5GO2C^<"S9,`4B._;H=(6!$B<^PJ"H
M_6D'(%]_D7_V=(PZ$Z.BNT8#>(%4,\[H1^I`!ST2O&A45@C1F;!!?YV?0NS,
MR9RQ@LT>*5A)\</B*Y73GJ*5NIC/F=(!JSQFL0F7EUSBE/;%@WY#X!]JHDG,
MHKD!:9IXIWW<+(<>@,,0_3T=DF1ZA'[H'T(T]$VA#S&'X1#S!H345%@'T3_1
M@FD_'-T'!0ZY/PH<R(\WWF:MJMMR7@LM%)RAX/1>.&BV0U,&RWV=D<`-9B1Q
M7GTKMW-5KLR*(NLZLHJ0M2%C!I>:4<2I5HC7K1<SFW`XC"RU*B+^A9R-]'TO
M<ISB+XD4&B9Q<]%@)DI;X@:W'C.X^M"@2WS3E"(LK075QZLB7Z@^7E';&YO;
M2SJ.O@JD6_6U27O.M@]LP@LK5]IDG`A75%E;&\?C_3G&VF43EJU<J6#^.V+^
M#"%L178Q0I@I0VA\!#/37'2W48PT%T7Z[C;ZF>89C>(Y!78:VLQ!FS_&;<;#
MCMM\,F+3(-M<1B"FE`MX/I+2#L.XN3*/OD-4+0"DYV";M=5ZSRJ%)2GQ*F>P
MU"[%A<<Q`R?L)_AA<F%Y:LQ.8I&;X02(,I2#G(\"=?0U4!;&%=)MO5>2?<U"
MU+;%3"KPQGRGZTPJA!FX^[N2XHV<QB(GWM2H;^6'>WLLPL24AXUA2@FIP('-
M$O[&$*T"0W01KE=\VTPC0Z$$J%VRCE>%)H)JR&76-B>%9\#`B?U;I`V%YGB;
MR'VFI#$N+R>J$B=S^B2\N[B-,RYOX":\:6W%M`9.D$%1;!CK^DOT.#-78.E;
MF'"*5,T8HLT20D@^3(9'#`<CV<1<`%$/53**'(WQS5;(Y(?!^+JA`?(=049[
M`S8?8AI@8UT/VJNUFT4-.=O'2N3&EG;(=]U;15-<6?0+(#&B/DYQJKD?9&=F
MDAIUXCTN1_5G?X*UM:5?NK9`7&;26HXTP!(P<J86J%W<Z6,B7_)#XHS`L,XW
M+=)+VE:33M59/VUM'>SZ05M!-`TV^9,"P_V<)F0$L?>^^'W2.=>E%E:IA3UZ
M4C-AC9"\0C5P01V3A)H))1O;22=B47.TF%^07TAJF#1B-H+U8F(7KQUL-P*_
M/!/7ZV`[!5A]%ISY!?$J8U*6Q>?Y9YWQUNGD)FW>N(FT*;[4:P17;$C4AR9!
M7UH,^??;7:1&O[AF`J\B-;IW`T,Q3D=BJ3%5OSB0ET<&2]K3;U]C(I]'NGJ'
M/P1E_&6D6QYC7;>TAY*A[^8WH&P?@5MT8#<#O.:"G:$@).$^^#XV-$)SX'0I
M8`3[`X5_%?F!W0^`GW+D5Y#(!($SH(ID#N+>1">V\FW$_N#`MIB\X<2W)MDQ
MIQMU,R(:B:I6HJ(#'<[M.UKT(*ZM#^S688?+!ENU)S7(L[:*B^J5X/*FC`)9
M@V.(72>JZT,4.$);1[IT%*2L]SB.QQ``?&`!<+I>A!V@&\WP@+VGKDNP]PO.
M@;ZU4"_+:H,3\*@BV+\2G/>(_2MK5]@(P5Y&DCJ*^RV"UB*X:'D46`:\WA+8
M0^.,BI/K91;16HB+'O'VOE0_ZE$7G/4DCTMT_[%'>1[DTCY0\$O5>BSD:)J"
M?>B`_6]U706.%R'^5Y2(O8<X/XV#$E]X!&>/X/R4V/N)<T!.\0YS2/><)`5Z
ML;0?(=[QAH'=_<!W!'8/`'^:V(=*BB]>TL,4/!+6RT<%4%&S-12>@E14MGQ'
MNE5-00#I')1KD%Y!RB!]&:D6*8OZ`M*[^*Q'*J`O6>\0=J,1Z:^1)B,UHWP*
M4AO2J4AKT;\9:8^.@F-([],4+$3Z"CZ'D,Y)H"`,&DH^D[V'SV:DFY'6H=XV
MI/_4T5#QM".EYEN$%'X1RZ*2E27V[)RLDNQ<>]Z2;]&-LS$BII`,LYZH=?:)
M7)GYB\<EQL<9\G-&1NZZPE5+<4LIL"U8L"!)/Y_U<Z5E.UEOM=NW[25O31*6
M59%999FGDG-OQ[-VN:?:4^YFM_Z,11-(4!1^+"M4>CG67>GE\=3MKRK%`_@V
MKP\9U1Z?M[+"7<FA]B19>^&/9&V^TKVKREW&N<O9'>[2*M;M\WE]J((G#MN"
M=`7-.)5\WE.V$[\<'ZKIE+B*IR?&+?5MY^6@?G0Y67&Y,(Z1K2A%-_A]6N8N
MYWUN%#\`O$G@XROG<YX*=SP$B]TDER5=ML)BX+=%Y?;Y55ZL`NOGJZJ\/DY)
M&"7E[G+907QRGU3H<;Q_`5!+`0(4`!0`!``(`+A;:QN_8QC1"@D``"`1```,
M````````````(`````````!724Y?5U)!4"Y%6$502P4&``````$``0`Z````
&-`D`````
`
end

[ Section: 1/1  File: WW.ZIP  Encoder: Wincode v1.5 ]